home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19971216-19980424
/
000042_news@newsmaster….columbia.edu _Sat Jan 3 22:32:26 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id WAA29089
for <kermit.misc@watsun.cc.columbia.edu>; Sat, 3 Jan 1998 22:32:25 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id WAA05614
for kermit.misc@watsun; Sat, 3 Jan 1998 22:32:24 -0500 (EST)
From: jwmanly@unix.amherst.edu (John W. Manly)
Newsgroups: comp.protocols.kermit.misc
Subject: Problem with CKERMIT TRANSMIT
Date: 4 Jan 98 02:37:24 GMT
Organization: Amherst College
Lines: 32
Message-ID: <34aef5e4.0@amhnt2.amherst.edu>
NNTP-Posting-Host: amhnt2.amherst.edu
X-Newsreader: TIN [version 1.2 PL2]
Path: news.columbia.edu!sol.ctr.columbia.edu!news.uoregon.edu!news.rediris.es!news-ge.switch.ch!news-fra1.dfn.de!Cabal.CESspool!bofh.vszbr.cz!cpk-news-hub1.bbnplanet.com!cam-news-feed1.bbnplanet.com!news.bbnplanet.com!alpha-nt.newbedford.k12.ma.us!gatekeeper.umassd.edu!umass.edu!amhnt2.amherst.edu!abby.unix.amherst.edu!jwmanly
Xref: news.columbia.edu comp.protocols.kermit.misc:8209
Hi, all. I've been running into a very frustrating problem with the CKERMIT
TRANSMIT command when used over TCP/IP to a port other than the standard
TELNET port (port 23).
In particular, I'm trying to use CKERMIT to "force feed" a message into
our NNTP news server, so I've tried just doing the following:
set host news-server nntp
output post\13
pause
transmit message.txt
pause
output .\13
output QUIT\13
quit
But the TRANSMIT operation never seems to work, though the rest of the
script does work. Sometimes it seems that some of the input file gets
lost, other times nothing at all seems to be transmitted by the TRANSMIT
line. I've tried "set transmit pause 1000" to make sure the target
buffers weren't being overwhelmed, but nothing seems to help.
Just for laughs, I tried this to two different mail servers's SMTP
ports, and I get the same kind of results -- the TRANSMIT command does
not seem to handshake (or something) with the other end. But if I
use this script to port 23 of a host, then it works fine.
Is there something about a connection to a non-TELNET port on a remote
host that makes the TRANSMIT command problematical?
- John W. Manly <JWMANLY@AMHERST.EDU> Acting Director, Amherst College ACC